We have created this complete vendor invoice processing checklist as a 5-stage list of verification items for AP teams to ensure each invoice is captured and processed accurately before payment is approved.
| Who this is for: AP managers, accounts payable teams, and finance controllers responsible for vendor invoice verification |
| What you get: A print-ready PDF version of this checklist is available free at the bottom of this page |
This complete checklist covers five stages: receipt, data validation, PO matching, approval routing, and payment and record-keeping. In addition, we have also covered the red flags that trigger a hold, additional checks for high-value and new-vendor invoices, and a monthly self-audit sweep.
Invoice errors cost more to fix after payment than before it. If an AP process does not have a structured verification checklist, there will be duplicate invoices, quantity mismatches, and price changes that go unnoticed until it’s too late.
At Serina, we have created an actionable set of items to check at each stage of your invoice processing flow. This works for all enterprises regardless of their size and the number of invoices they process each month. But for a significantly larger number of invoices, it is always an option to automate Accounts Payable to avoid manual checks at every step of the invoice journey.
How to Use This Checklist
The checklist is designed to be used per invoice on every cycle. Each stage of the checklist must be completed before moving to the next. Items marked❗are hard-stop checks: if one fails, the invoice goes on hold until the issue is resolved. The automation section near the bottom explains which of these checks Serina runs automatically, so your team only handles the exceptions that really need a human decision.
Stages for using Vendor Invoice Processing Checklist
Stage 1 – Invoice Receipt Verification❗
Before even starting the data collection from the invoices, make sure the invoice came through a legitimate, traceable channel.
☐ Invoice received via an approved channel – authorized email address, vendor portal, EDI feed, or designated shared inbox. Not a personal inbox, a forwarded message chain, or an unregistered sender address.
☐ Sender identity confirmed – the ‘from’ address or portal login corresponds to the vendor’s registered contact on file. Verify every new or unrecognized sender before the invoice even enters the processing queue.
☐ Invoice logged in the AP system on receipt – date, time, and source channel recorded. No invoice enters the queue without a log entry; this is the start of the audit trail.
☐ Invoice assigned a unique internal reference number – prevents duplicate processing if the same invoice arrives via more than one channel.
☐ Immediate duplicate check run – confirm this invoice number has not already been submitted or paid. Same vendor, same amount, same date with a different invoice number is also a duplicate flag.
Stage 2 – Invoice Data Validation❗
Verify that the invoice contains all required information before matching it against a purchase order or routing it for approval.
☐ Vendor name matches registered vendor master exactly – not a variation, abbreviation, or informal trading name unless documented.
☐ Vendor address and contact details are present and match the vendor master file.
☐ Unique invoice number is present and follows the vendor’s documented format. Missing or non-standard billing numbers must be queried with the vendor before processing.
☐ Invoice date and payment due date clearly stated and reasonable – invoices dated more than 90 days in the past should be reviewed for legitimacy before acceptance.
☐ Description of goods or services is specific and identifiable – not vague or generic. ‘Consulting services – Q2’ with no further detail requires explanation before approval.
☐ Quantities and unit prices individually listed at line-item level – not a lump-sum total only.
☐ Subtotals, taxes, and final total verified by recalculation – a total that does not match the sum of line items is an immediate hold.
☐ Tax identification or VAT number present where required and corresponds to the vendor’s registered number.
☐ Currency clearly stated and matches the vendor agreement – invoices in an unexpected currency require confirmation before processing.
☐ Bank details on the invoice match the vendor’s registered payment details. Any change to bank account information must be verified directly with the vendor via a known contact channel before updating the vendor master – not from the invoice alone.
Stage 3 – PO Matching and 3-Way Match Verification❗
For PO-backed invoices, the invoice must match both the PO and GRN before it can be approved. For a full explanation of the 3-way matching process, see our three-way matching guide.
☐ The PO number is on the invoice in proper format, and it matches an active PO in the system. Return the invoices that don’t have a valid PO back to the vendor for correction.
☐ Items, quantities, and unit prices match the PO at line-item level, not just in total. A total that matches while individual lines differ is still a discrepancy.
☐ Goods receipt note (GRN) confirmed – Ensure the goods or services in the GRN were actually received and signed off. Do not approve payment for goods that were not received or partially received.
☐ Partial delivery: if only part of the PO has been fulfilled, the invoice must match the received quantity only – not the full PO value. Flag invoices that bill the full PO amount against a partial delivery confirmation.
☐ Price variance check – if the invoice price differs from the PO, check whether the variance falls within the configured tolerance threshold. Variances within tolerance proceed. Variances above threshold are held, and an exception is raised.
☐ Non-PO invoices (indirect spend, utilities, emergency purchases) – GL code and cost center are assigned by an authorized team member before the invoice is routed for approval.
Stage 4 – Approval Routing and Exception Handling❗
Route the validated invoice to the correct approver. Approver assignment is determined by invoice amount, cost center, and vendor category – not by whoever is available.
☐ Invoice routed to the correct approver per the approval matrix – verify approver, amount threshold, and cost center assignment are all consistent.
☐ Approval deadline set – invoices approaching their payment due date are flagged urgently to the approver to prevent late payment.
☐ Approval confirmation received and timestamped in the system – verbal approvals are not valid. Every approval must be recorded with approver name, date, and time.
☐ Exception clearance confirmed – if the invoice was flagged at Stage 2 or Stage 3, confirm the exception is fully resolved before routing for approval, not simply acknowledged.
☐ Segregation of duties confirmed – the person who approves the invoice must not be the same person who raised the original PO, and must not have sole authority to process the subsequent payment. Indicate any overlap immediately.
☐ Invoices returned to vendor are logged as ‘on hold’ with the reason and return date recorded. Do not manage holds via email chains.
Stage 5 – Payment Scheduling and Record-Keeping❗
Once approved, the final stage covers payment scheduling, disbursement, and filing.
☐ Payment due date and early payment discount window confirmed – check whether a 2/10 net 30 or similar discount term applies and organize accordingly.
☐ Payment method corresponds to the vendor’s registered preference and the invoice’s bank details – ACH, bank transfer, or other method per the vendor agreement.
☐ Payment scheduled in the ERP with the correct posting date, GL code, cost center, and vendor reference.
☐ Payment confirmation sent to the vendor after disbursement – via the vendor portal, remittance email, or the AP system’s automated notification.
☐ Invoice marked as paid in the AP system with payment date, amount, and reference number recorded.
☐ All documents filed together – original invoice, PO, GRN, approval record, and payment confirmation stored with the correct vendor and date references.
☐ Recurring vendor flag – if this is a recurring vendor, flag the invoice for inclusion in the next monthly vendor statement reconciliation.
Related guide: For the full vendor invoice management process, see our vendor invoice management guide.
10 Red Flags That Should Stop Payment on Any Invoice
These warning signs require an immediate payment hold and escalation to the AP manager or finance controller. They are reasons to investigate before proceeding – not automatic rejections. Billing schemes are among the most commonly detected categories of occupational fraud, and these checks are the primary manual controls against them.
| # | Red Flag | Why it warrants investigation |
| 1 | Bank account details changed on or with an invoice | Banking-change fraud is the most common AP fraud vector. A fraudster substitutes their account for the real vendor’s. Always verify directly with the vendor via a known phone number or signed document – never from an emailed invoice or attachment alone. |
| 2 | Invoice from a vendor not in the approved vendor master | May indicate a fictitious vendor scheme. No invoice from an unregistered vendor should be approved without completing the vendor onboarding process first. |
| 3 | Duplicate invoice number from the same vendor | Duplicate submissions – whether accidental or deliberate – result in double payment if not caught. Even a one-character variation in the invoice number warrants verification before payment. |
| 4 | Invoice total does not match the sum of line items | A deliberately inflated total is a common billing error or fraud indicator. Always recalculate before approving. |
| 5 | Invoice for goods or services with no corresponding PO | May indicate an unapproved purchase routed through AP. Require a retrospective PO or written authorisation from the budget owner before any payment. |
| 6 | Invoice dated more than 90 days ago | Very old invoices may be resubmissions of already-paid invoices, errors in the vendor’s billing system, or deliberate attempts to claim against a closed accounting period. Verify before accepting. |
| 7 | Rounded invoice amounts with no line-item detail | Legitimate invoices specify what was delivered. A round-sum total with a vague description (‘services – $5,000’) requires a detailed breakdown before approval. |
| 8 | First invoice from a new vendor for a large or unusual amount | High-value first invoices from new vendors warrant the additional checks in the new vendor section below, plus a second-pair-of-eyes approval regardless of the standard threshold. |
| 9 | P.O. Box listed as the only address on the invoice | Not automatically fraudulent, but when combined with other flags – a new vendor, an unusual amount, or a missing PO reference – warrants additional verification of the supplier’s registered address. |
| 10 | Invoice submitted directly to an approver, bypassing the AP intake channel | Invoices that bypass the standard channel bypass the controls that protect against fraud and errors. Return to sender and route through the correct intake process before any further action. |
New Vendor First Invoice: Additional Checks
The first invoice from any vendor not previously paid carries additional risk. Run these checks before the first payment is processed, in addition to the standard 5-stage checklist above.
☐ Vendor onboarding is complete – tax forms, banking details, as well as any required compliance documents are on file before any invoice is processed.
☐ Business registration verified – confirm the vendor is a registered legal entity. For significant vendor relationships, verify the company registration number and trading address against a company registry or credit bureau.
☐ Banking details received via a secure, verifiable channel – a vendor onboarding form, verified portal submission, or a signed letter from a recognized contact. Not from the invoice alone.
☐ Contract or purchase agreement on file – a signed agreement documenting what was ordered, at what price, and under what terms, before any payment is approved.
☐ Second-pair-of-eyes approval – for the first payment to any new vendor, require authorisation from a manager or controller above the standard approval threshold, regardless of the invoice amount.
Monthly AP Self-Audit Checklist
Run this internal controls sweep once a month. For most teams it takes under two hours and surfaces complications before they become expensive. For complete AP auditing guidance, see our AP auditing guide.
☐ Duplicate payment report run – look for any invoices paid twice in the past 30 days. Identify the cause and confirm recovery or credit is in progress.
☐ Exception queue reviewed – which vendors or invoice types generated the most exceptions this month? A consistent pattern from one vendor signals a data quality or relationship issue worth addressing directly.
☐ Open invoices checked against payment terms – identify approaching or past-due invoices not yet processed and escalate immediately.
☐ GL code mappings verified as current – chart of accounts changes, new cost centres, and team reorganisations make GL assignments stale. Confirm the current mapping is accurate.
☐ Approval matrix confirmed – verify that the approval matrix still reflects current roles. Approvers who have left or changed roles should have active backup delegates assigned.
☐ Vendor master spot-check – pull a sample of 10-15 vendor records and confirm that name, address, bank details, and tax number are accurate and match your contracts on file.
☐ Outstanding POs checked – identify POs raised but not yet invoiced and verify if the goods or services are still expected.
When to Proceed vs. When to Escalate
| Situation | Action | Who handles it |
| Price or quantity variance within configured tolerance | Proceed – auto-approve if system is configured for tolerances | System or AP team |
| Price or quantity variance exceeding tolerance | Hold – raise exception, contact vendor or purchasing team | AP team plus vendor |
| PO number missing on a PO-backed invoice | Return to vendor – do not process without a valid PO reference | AP team |
| Bank account change request | HOLD – verify with vendor via a known, independent contact before any update | AP Manager plus Finance Controller |
| Invoice from an unregistered vendor | Hold – complete vendor onboarding before any processing | AP Manager plus Procurement |
| Duplicate invoice number detected | Hold – verify with vendor whether this is a resubmission or a new invoice | AP team |
| Any of the 10 red flags triggered | Hold – escalate for AP manager review before any action | AP Manager |
| Segregation of duties conflict identified | ESCALATE IMMEDIATELY – requires remediation before processing continues | Finance Controller plus Compliance |
How Serina Automates These Checklist Steps
The checklist above describes what AP teams check when the process is manual. When vendor invoice processing is automated with Serina, most of these checks run on every invoice without a team member working through each item one by one.
- Stage 1 (Receipt): Serina ingests invoices from email, vendor portals, EDI feeds, and scan folders, logs them automatically, and runs an immediate duplicate check on arrival.
- Stage 2 (Validation): AI and OCR extract line-item data and run validation rules – checking vendor master match, field completeness, tax number format, and arithmetic accuracy prior to any human review being triggered.
- Stage 3 (PO Matching): Serina matches invoices against purchase orders and goods receipts at line-item level. Configurable tolerance thresholds auto-approve minor variances; genuine exceptions are routed to the right person.
- Stage 4 (Approval Routing): Validated invoices are routed automatically to the correct approver by amount, cost center, vendor, or invoice type. Every approval is timestamped and logged.
- Stage 5 (Payment and Record-Keeping): Approved invoices are posted to the ERP – SAP, Oracle, or Microsoft Dynamics – with correct GL coding, cost center, and vendor references. Payment confirmation is issued automatically.
For teams still working through these stages manually, automation does not replace the checklist – it runs the checklist without manual effort on the majority of invoices, so your team focuses on the exceptions that require actual judgment. See how Serina automates vendor invoice processing.
Download the Free Vendor Invoice Processing Checklist (PDF)
A print-ready, single-page PDF version of this checklist is available as a free download – formatted for desk use or team distribution.
If you want to see how Serina automates the checks on this list across your full invoice workflow, schedule a consultation here.
Final Thought
A vendor invoice processing checklist is only as useful as its consistent adoption. Worked through on every invoice, every cycle, it provides genuine protection against the errors, fraud, and compliance gaps that cost AP teams time and money to fix after the fact. The same discipline that makes a manual checklist effective is also what makes AP automation worthwhile: every check that runs automatically on every invoice is a check that cannot be skipped, forgotten, or rushed past at month-end.
If your team is working through this checklist manually, the volume itself is an argument for automating it. See what Serina automates in vendor invoice processing.
Frequently Asked Questions
Q1. What should be checked on a vendor invoice before payment?
Before payment, an invoice should pass five verification stages: receipt confirmation (correct channel, logged, duplicate check), data validation (vendor details, invoice number, amounts, tax), PO matching (quantities and prices against the PO and goods receipt at line-item level), approval (from the correct authorized approver per the approval matrix), and payment scheduling (correct method, due date, and ERP posting). Any of the 10 red flags listed in this guide should trigger an immediate hold.
Q2. How do you verify a vendor invoice?
Invoice verification involves: confirming the vendor is registered in the vendor master, checking that all required fields are present and accurate, comparing the invoice against the purchase order and goods receipt at line-item level, verifying the arithmetic, and confirming that bank details match the vendor’s registered information. Any discrepancy stops the invoice at that stage until resolved.
Q3. What are the most common vendor invoice errors?
• Arithmetic errors – totals that do not match the sum of line items
• Quantity mismatches – billing for more than was delivered
• Price discrepancies – rate changes not reflected correctly on the invoice
• Missing PO numbers on PO-backed invoices
• Duplicate submissions – the same invoice sent twice via different channels
• Stale invoices dated months before submission – often resubmissions of already-paid invoices
Q4. What are red flags on a vendor invoice that should stop payment?
The 10 most significant red flags are listed in the table in this guide. The most critical are: bank account details changed on or with an invoice (the most common AP fraud vector), invoices from unregistered vendors, duplicate invoice numbers, and invoices that bypass the standard AP intake channel. Any single red flag warrants a hold and AP manager review before any payment action.
Q5. What extra checks apply to a new vendor’s first invoice?
First invoices from new vendors require: confirmation that vendor onboarding is complete (tax forms, banking details verified via a secure independent channel, contract on file), business registration verification, bank details confirmed from a source other than the invoice itself, and a second-pair-of-eyes approval from a manager above the standard threshold regardless of the invoice amount.
Q6. Which checklist steps can be automated?
All five stages can be automated. Stages 1 to 3 (receipt, validation, and PO matching) can run without human involvement for compliant invoices. Stage 4 (approval routing) is automated, with human review only for exceptions and invoices above specific thresholds. Stage 5 (ERP posting and record-keeping) can be fully automated. The 10 red flag checks can be built into system validation rules to run automatically on every invoice. See how Serina automates vendor invoice processing.
